failure 138:
Requirement failed: {setuid.05.02} error not met because its predicate (( priority_coverage == Priority_ReallyLow || ( priority_coverage == Priority_Unknown && setuid_spec == -1 ) ) && ( uid_coverage != Id_RealId && uid_coverage != Id_SavedSetId )) is false while error code EPERM is set ;
| location |
| trace |
/var/opt/lsb/test/olver-core/2014-01-29_05-08-38/process_meta_user_scenario.utz (process_meta_user_scenario.utt), line 151731 |
| occurence |
| scenario |
process_meta_user_scenario |
| specification function |
setuid_spec() |
| parameter value |
CallContext context = [pid=5172,thr=b74d9700] |
| parameter value |
UidT uid = 0 |
| parameter value |
ErrorCode * @errno = EOK |
| parameter value |
ErrorCode * errno = EPERM |
| return value |
(IntT) -1 |
coverage
& branch |
C
( Id, priority ) == ( Id_SavedSetId, Priority_ReallyLow ) |
| properties |
| REQ failed |
setuid.05.02 |
| kind |
POSTCONDITION_FAILED |
similar known bug(s)
|
The setuid() function sets the real user ID, effective user ID, and the saved set-user-ID
of the calling process to the value, specified as its argument.
According to LSB, if this argument equals to the real user ID or the saved set-user-ID,
setuid() shall set the effective user ID to this value.
But on the target machine setuid() fails when trying to set the effective user ID to the
saved set-user-ID value.
Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102.
|
|